Remote video triggering and tagging

ABSTRACT

A video collection system collects and sends metadata related to video data such that recording may be triggered and tagged. The video collection system utilizes a mobile broadband network (such as a cellular network) to send metadata, receive triggers, and perform other functions while the video collection system is in the field. The video collection system broadly comprises a plurality of video cameras and a video collection manager. The video cameras each include a mobile broadband modem or other wireless communication element for sending metadata messages. In some embodiments the mobile broadband modem may also send still images, audio data, and video data.

RELATED APPLICATIONS

This application is a continuation patent application of U.S. patentapplication Ser. No. 16/534,761, filed Aug. 7, 2019, which claimspriority to U.S. Provisional Patent Application No. 62/716,277 filed onAug. 8, 2018, and U.S. Provisional Patent Application No. 62/836,913filed on Apr. 22, 2019, the disclosures of which are incorporated hereinby reference.

Embodiments and/or features of the invention described in the presentdocument may be used with the subject matter disclosed in commonlyassigned U.S. Pat. No. 8,781,292, filed Sep. 27, 2013, issued Jul. 15,2014 and entitled “COMPUTER PROGRAM, METHOD, AND SYSTEM FOR MANAGINGMULTIPLE DATA RECORDING DEVICES” (“the '292 Patent”); and commonlyassigned U.S. Pat. No. 9,253,452, filed Aug. 14, 2013, issued Feb. 2,2016, and entitled “COMPUTER PROGRAM, METHOD, AND SYSTEM FOR MANAGINGMULTIPLE DATA RECORDING DEVICES” (“the '452 Patent”). The '292 Patentand the '452 Patent are hereby incorporated by reference in theirentirety into the present application.

BACKGROUND 1. Field

Embodiments of the invention are broadly directed to video collectionand storage. More specifically, embodiments of the invention aredirected to the collection and sending of metadata related to video datafrom video cameras to a remote video collection manager via a mobilebroadband network.

2. Related Art

The transmission of video data is burdensome on bandwidth and memoryresources. Similarly, the backend processing of video data is processorintensive, requiring the processor to analyze, tag, and extract certainportions of the video data. For large systems of video camera (such as alaw enforcement fleet, school, or hospital, as examples) thistransmission and processing can cause significant delays or beprohibitive in most instances. For example, most law enforcementagencies transfer video files from a law enforcement vehicle to a backoffice using a standard Wi-Fi connection. This process is adequate forsmall files and uncongested Wi-Fi networks. However, for large files(such as those created with high-definition cameras) and multiple camerasystems, Wi-Fi is slow and unreliable. Thus, many law enforcementagencies began having the law enforcement office physically transferringa memory card to the back office, but in this there is a chance oflosing the data and requires the law enforcement officer to remember tobring and return the memory card.

What is lacking in the prior art is an efficient and intelligent systemto manage video transmission and processing from video cameras. Anadministrator with information about the video data recorded, andremotely instructing the recordings, can more specifically request videodata from the video camera. This will reduce transfer time and back-endprocessing time.

SUMMARY

Embodiments of the invention solve these problems by providing a videocollection system collects and sends metadata related to video data suchthat recording may be triggered and tagged. The video collection systemutilizes a mobile broadband network (such as a cellular network) to sendmetadata, receive triggers, and perform other functions while the videocollection system is in the field. The video collection system broadlycomprises a plurality of video cameras and a video collection manager.The video cameras each include a mobile broadband modem or otherwireless communication element for sending metadata messages. In someembodiments the mobile broadband modem may also send still images, audiodata, and video data in certain circumstances as discussed below. Thevideo camera may also be associated with a video dock for the transferof video data to the video collection manager. The video collectionmanager is communicatively coupled with one or both of the plurality ofcameras and the plurality of camera docks. In some embodiments, thecamera can be instructed or controlled by the video collection managerand can transmit captured metadata, such as to a memory associated withthe video collection manager. The video collection manager can transmittrigger information, tag information, and other information that willexpedite the later processing and transfer of video data. The capturedvideo is transmitted or otherwise downloaded to the camera dock, and thevideo collection manager can instruct or otherwise control transmissionof the captured video from the video camera dock and to the memoryassociated with the video collection manager.

A first embodiment of the invention is broadly directed to a videocamera comprising a lens assembly, a non-volatile memory, a mobilebroadband modem, and a processor. The processor is configured toreceive, from a remote video collection manager via the mobile broadbandmodem, a trigger message indicative of a triggering event remote fromthe video camera. The processor is further configured to instruct videodata from the lens assembly to be stored in the non-volatile memory inresponse to the trigger message. The processor is further configured tosend, to the remote video collection manager via the mobile broadbandmodem, a metadata message indicative of the video data from the lensassembly. The processor is further configured to receive, from theremote video collection manager via the mobile broadband modem, atrigger termination message based at least in part of the metadatamessage. The processor is further configured to send, to the remotevideo collection manager via the mobile broadband modem, apost-recording metadata message. The processor is further configured tocease storage of the video data in the non-volatile memory.

A second embodiment of the invention is broadly directed to acomputerized method of capturing video data by a video camera, thecomputerized method comprising: receiving, by a mobile broadband modemof the video camera, an administrator-initiated trigger via a mobilebroadband network; initiating a recording of video data; sending, to avideo collection manager via the mobile broadband modem, a metadatamessage indicative of metadata associated with the video data;terminating the recording of the video data in response to terminationof the administrator-initiated trigger; sending, to the video collectionmanager via the mobile broadband modem, a trigger-complete metadatamessage; and storing the video data for later transfer.

A third embodiment of the invention is broadly directed to a videocollection system comprising a video camera and a video collectionmanager. The video camera includes a mobile broadband modem. The videocollection manager is communicatively coupled to the video camera viathe mobile broadband modem of the video camera. The video collectionmanager is configured to send a first triggering message to the videocamera indicative of an administrator-initiated trigger. The videocamera is configured to record a first set of video data based upon thefirst triggering message. The video collection manager is configured toreceive a second triggering message from the video camera indicative ofa user-initiated trigger. The video camera tags a second set of videodata based upon the second triggering message. The video collectionmanager is configured to receive a periodic metadata message from thevideo camera indicative of video data being recorded by the videocamera.

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Other aspectsand advantages of the invention will be apparent from the followingdetailed description of the embodiments and the accompanying drawingfigures.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

Embodiments of the invention are described in detail below withreference to the attached drawing figures, wherein:

FIG. 1 is a schematic diagram illustrating internal components of avideo camera configured to communicate with a remote video collectionmanager via a mobile broadband network;

FIG. 2 is a schematic diagram illustrating a video collection system ofwhich the video camera may be a component;

FIG. 3 is flow diagram illustrating exemplary steps performed by thevideo camera; and

FIG. 4 is a flow diagram illustrating exemplary messages that may passbetween the video camera and the video collection manager via the mobilebroadband network.

The drawing figures do not limit the invention to the specificembodiments disclosed and described herein. The drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the invention.

DETAILED DESCRIPTION

The following description of the invention references the accompanyingdrawings that illustrate specific embodiments in which the invention canbe practiced. The embodiments are intended to describe aspects of theinvention in sufficient detail to enable those skilled in the art topractice the invention. Other embodiments can be utilized, and changescan be made without departing from the scope of the invention. Thefollowing detailed description is, therefore, not to be taken in alimiting sense.

In this description, references to “one embodiment,” “an embodiment,” or“embodiments” mean that the feature or features being referred to areincluded in at least one embodiment of the technology. Separatereferences to “one embodiment,” “an embodiment,” or “embodiments” inthis description do not necessarily refer to the same embodiment and arealso not mutually exclusive unless so stated and/or except as will bereadily apparent to those skilled in the art from the description. Forexample, a feature, structure, act, etc. described in one embodiment mayalso be included in other embodiments, but is not necessarily included.Thus, the current technology can include a variety of combinationsand/or integrations of the embodiments described herein.

Embodiments of the invention may be embodied as, among other subjectmatter, a method, a system, or a set of instructions embodied on one ormore computer-readable media. Computer-readable media include bothvolatile and nonvolatile media, removable and nonremovable media, andcontemplate media readable by a database. For example, computer-readablemedia include (but are not limited to) RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile discs (DVD),holographic media or other optical disc storage, magnetic cassettes,magnetic tape, magnetic disk storage, and other magnetic storagedevices. These technologies can store data temporarily or permanently.However, unless explicitly specified otherwise, the term“computer-readable media” should not be construed to include physical,but transitory, forms of signal transmission such as radio broadcasts,electrical signals through a wire, or light pulses through a fiber-opticcable. Examples of stored information include computer-useableinstructions, data structures, program modules, and other datarepresentations.

Different forms of computer-readable media store data in different ways.For example, volatile storage media such as RAM may retain data only aslong as it is powered, while non-volatile media such as flash memoryretain data even when powered off. Furthermore, some forms of computerstorage media are write-once, read many (WORM), such that data can bestored to them but not erased or overwritten. For some forms of WORMmedia, data can be recorded in multiple sessions, where the data fromone session is appended to the data from the previous session. Otherforms of media may be indefinitely rewriteable. Some forms of media maybe encrypted, such that data is written to them encrypted by anencryption key (which can correspond to the device, the user, or beunique in some other way) and data read from them is scrambled unlessdecrypted with the corresponding decryption key.

Additionally, storage media can be made tamper-resistant such that it isdifficult or impossible to alter or erase data stored to them, or toprevent reading data except by authorized means. WORM media or encryptedmedia, as described above are one way to make storage media tamperresistant. Another way is to make storage media physically difficult toremove, such as by covering them with epoxy after they have beeninstalled. Other methods of making storage resistant tamper resistantare also known in the art and can be used.

Turning first to FIG. 1, a system diagram showing a video camera 100 isdepicted schematically. The video camera 100 generally comprises acamera housing 102 and various internal components. The camera housing102 may take any of numerous form factors, such as those shown in FIG. 2and discussed below. For example, the camera housing 102 may be mountedon a person (either directly or via clothing or some other equipment),in a vehicle oriented outward, in a vehicle oriented inward, on a staticstructure, a head-mounted display form factor incorporating an eyepiece,a low profile, lapel- or epaulet-mounted form factor, or other formfactor.

Mounted inside the camera housing 102 is at least one lens assembly 104.The lens assembly 104 is configured to capture video data. In someembodiments, additional lens assemblies may also be present. Each oflens assembly 104 is operable to provide a video feed of video data.While reference is made to “video data” and “video feeds,” In someembodiments, lens assemblies 104 may instead, or in addition, recordstill image data.

In certain embodiments, camera housing 102 may also include a display106. In some embodiments, display 106 may be a monocular display fordisplaying the video feed from lens assembly 104, replaying recordedvideo data, or displaying other information. The other information mayinclude metadata associated with the video data. In other embodiments,the display 106 is a glassless holographic display. Where present,display 106 generally may be any form of image display technology nowknown or hereafter discovered or invented. In some embodiments, display106 is not integrated into camera housing 102, but rather removablyattached, either directly or via a cable or wireless connection.

In some embodiments, camera housing 102 will also have an attachmentstructure 108 for connecting to one of a variety of suitable mounts.This attachment structure 108 may be purely mechanical or mayincorporate data connections for connection to display 106, and/or otherperipheral units. Examples of such attachment structures 108 includescrew mounts, clip mounts, ball-and-socket mounts, friction mounts, andsnap mounts. Any type of mounting hardware, now known or hereafterdiscovered may be used. The attachment structure 108 may be configuredto be secured to a person, a vehicle, a stand, or other equipment.

In some embodiments, power supply 110 is mounted in camera housing 102.In some embodiments, power supply 110 is a set of rechargeable batterycells. These cells can be removable for recharging or chargeable via anexternal connection. In other embodiments, power supply is one or morenon-rechargeable batteries. In still other embodiments, power supply 110is a fuel cell or micro-turbine. Any form of power supply, now known orhereafter invented may be used as power supply 110.

In some embodiments, the camera housing 102 also contains processor 112and associated controller circuitry. In various embodiments, processor112 performs different functions associated with the operation of thecamera unit including video encoding, trigger event detection, storagemanagement, and input/output (I/O) control, as well as other functionsknown in the art. Processor 112 may take the form of a microcontroller,microprocessor, or special-purpose controller circuitry. Processor 112may also incorporate one or more computer-readable media for storingdevice firmware. Processor 112 is electrically coupled to power source110, and communicatively coupled to lens assembly 104 as well as variouscomponents installed in camera housing 102, including storage memoriessuch as volatile memory 114 and non-volatile memory 116, sensors such assensor 118, and I/O ports and controllers such as I/O unit 126. Oneexemplary method of operation for processor 112 is depicted in FIG. 3.

Encoded video data and other data processed by processor 112 may bestored in one or more memories such as volatile memory 114 ornon-volatile memory 116. In one embodiment, video is recordedcontinuously, along with any relevant metadata, and stored in volatilememory 114. When a triggering event occurs (either locally, or receivedas a message from a remote device, as discussed in depth below), thecontents of volatile memory 114 are transferred to non-volatile memory116, and incoming video is also stored in non-volatile memory 116. Inother embodiments, two non-volatile or volatile memories are used. Inyet other embodiments, a single memory is used. In some single-memoryembodiments, all video data is stored to non-volatile memory 116. Inother single-memory embodiments, a triggering event initiated therecording and storage of data. In some embodiments, non-volatile memory116, volatile memory 114, or both provide authenticated,tamper-resistant storage such that recorded data can be used as evidencein legal proceedings. In some embodiments, processor 112 uses adevice-specific key to digitally sign or otherwise authenticate videorecordings. In some embodiments, non-volatile memory 116 is a removablememory card. In some such embodiments, non-volatile memory 116 iswrite-once, read-many (WORM) memory. In general, the storage memoriesused in embodiments of the invention can be any data storage media knownin the art as described herein or invented in the future. In someembodiments, camera housing 102 has no persistent storage memory, andvideo data that is to be retained is transmitted in real time over anetwork to a remote data store. In other embodiments, data to beretained is both stored locally and transmitted to a remote data store.

In some embodiments, additional sensors such as sensor 118 are presentin camera housing 102, or elsewhere. Such sensors 118 may provide datato supplement the video data provided by lens assembly 104. Examples ofsuch sensors include a microphone for recording audio data, a radioreceiver for recording radio transmissions, a global-positioning system(GPS) receiver for recording position data, one or more accelerometersfor recording movement and acceleration data, and a radio-frequencyidentifier (RFID) receiver for recording the presence of nearby RFIDtags.

In some embodiments, the camera housing 102 may also contain aninput/output (“I/O”) unit 120. The I/O unit 120 may allow additionalmodules such as those containing additional sensors to be attached. Insome embodiments, I/O unit 120 allows data from storage memories 114 and116 to be transferred off of the device. In other embodiments, it allowsprocessor 112 to be reprogrammed. In yet other embodiments, it allowspower supply 110 to be recharged. It will be apparent to a personskilled in the art that I/O unit 120 may perform all of these functions,individually or in parallel. For example, the video camera 100 may beinserted into a camera dock (not illustrated) for recharging andtransfer of video data.

In some embodiments, the video camera 100 comprises a mobile broadbandmodem 122. A mobile broadband modem 122 is a type of modem that allowsthe video camera 100 to receive Internet access via a mobile broadbandconnection. The video camera 100 includes a mobile broadband modem 122or is otherwise communicatively coupled with a mobile broadband modem122. The video camera 100, via the mobile broadband modem 122, sendsstatus messages (which may be periodic, based upon a user-initiatedtrigger, or both) and receives status messages and instructions (whichmay be periodic, based upon an administrator-initiated trigger, athird-party-initiated trigger, or some combination thereof).

The mobile broadband modem 122 communicates with a mobile broadbandnetwork 124. In embodiments, the mobile broadband network 124 is acellular network. Examples of cellular networks include Code DivisionMultiple Access (“CDMA”), Global System for Mobile communications(“GSM”), Orthogonal Frequency-Division Multiplexing (“OFDM”), variationsthereof, and other cellular networks. The mobile broadband network 124may use any of various data transmission protocols, presently existingor hereafter invented. Examples of data transmission protocols include2G, 3G, 4G, 4G LTE, and 5G.

A video collection manager 126 is communicatively coupled with themobile broadband network 124. The video collection manager 126 is acentralized or regional device or computer program, such as acloud-based storage system. The video collection manager 126communicates with the video cameras to determine what video data isbeing recorded, trigger the recording and saving of certain video data,instruct tags to be added to the video data for later retrieval andtransfer, and other functions. The video collection manager 126 may alsotrack the location of the video camera 100, the status of the videocamera 100, and other information based upon periodic metadata messagessent from the video camera.

The mobile broadband network 124 is connected to the Internet asdiscussed above. Thus, the video collection manager 126 may be connectedvia the Internet or via the mobile broadband network 124 directly. Forexample, the video collection manager 126 may also include a mobilebroadband modem. As another example, the video collection manager 126may include a wired Internet connection. The video collection manager126 may be a server, a cloud-based computing device, a cloud-basedstorage system, a computing device at a headquarters or dispatchlocation, or other computing device.

Turning to FIG. 2, an exemplary video collection system is shown.Broadly, the video collection system includes a recording device manager200 and one or more component devices. Some embodiments of the inventioninclude a recording device manager 200 as described in commonly-assignedU.S. Pat. Nos. 8,781,292 and 9,253,452, both of which are incorporatedherein in their entireties. The recording device manager 200 may receivean indication that one video camera 100 has begun recording and instructother video cameras (or other recording devices) to also beginrecording. The recording device manager 200 may include a user controldevice 202 that allows the user to view, edit, save, and organize thevideo data.

As shown in FIG. 2, the video collection system may include aperson-mounted video camera 204, a vehicle-mounted video camera 206, ora static-mounted video camera 208, other video cameras, or somecombination thereof. The video camera 100, discussed herein, may be theperson-mounted video camera 204, the vehicle-mounted video camera 206,or the static-mounted video camera 208, or some other video camera. Thevideo camera 100,204,206,208 records video data and/or audio data. Thevideo camera includes a mobile broadband modem 122 or is otherwisecommunicatively coupled with a mobile broadband modem 122. For example,the mobile broadband modem 122 may be within (or otherwise associatedwith) the recording device manager 200, such that the messages describedbelow are sent with the recording device manager 200 as a conduitthereto. The video camera 100, via the mobile broadband modem 122, sendsstatus messages (which may be periodic, based upon a user-initiatedtrigger, or both) to the video collection manager 126 and receivesstatus messages and instructions from the video collection manager 126(which may be periodic, based upon an administrator-initiated trigger, athird-party-initiated trigger, or some combination thereof).

The video collection system may include a computer 210 or other externalstorage device. The video camera 100 may also send video data to thecomputer 210 or other video cameras, memory cards, external memory, or aback-end office. For example, a vehicle-mounted video camera 206 maytransfer a portion of captured video data to a body-mounted video cameraso as to expedite the upload of the captured video data when thebody-mounted video camera is docked for recharging (instead of relyingof the physical transfer of a memory card or the upload over Wi-Fi, asdiscussed above).

Turning to FIG. 3, exemplary steps performed by the video camera 100 areshown and described. As shown in FIG. 3, various communications to andfrom the video collection manager 126 are shown. These communicationsare made by the mobile broadband modem 122 via the mobile broadbandnetwork, as discussed above.

In Step 300, the video camera 100 initializes. The video camera 100initializes upon power up or other initialization. Alternatively powerup may be through an independent power cable from an external powersource (such as an automobile electrical system). In other embodiments,power up may be initiated by the user pressing (or otherwisemanipulating) a button or other power switch (not illustrated) on thevideo camera 100. In these embodiments, the video camera 100 may bepowered by an internal battery (e.g., power supply 110). Uponinitializing, based upon receiving power or an initializationinstruction as discussed above, the video camera 100 performs boot upfunctions and other initialization functions. These may includecommunication with external computing devices, interfacing with sensor,beginning internal processes, powering up internal devices such as thedisplay 106, checking for internal errors, and other initializationprocesses.

In Step 302, the video camera 100 sends a status message to the videocollection manager 126. The status message informs the video collectionmanager 126 of the availability of the video camera 100 to beginrecording if needed. The status message may also include otherinformation related to the video camera 100, as discussed below inrelation to FIG. 4.

In Steps 304, 306, and/or 308, triggers are received by the video camera100 from various sources. Triggers instruct a recording to begin, arecording to be saved, a recording to be tagged or marked (or otherwisehave certain metadata associated with it), or some combination thereof.Triggers may additionally, or alternatively, or in certain instances, beindicative that such an action has already been taken and are thus astatus update. Three exemplary types of triggers, as mentioned above,include user-initiated triggers, administrator-initiated triggers, andthird-party-initiated triggers. These are discussed in more depth below.Other types of triggers may also be used. Further, multiple differenttypes of triggers may be received subsequently and/or other differentoccasions. For example, a first trigger received may be anadministrator-initiated trigger and a second trigger received may be athird-party initiated trigger. The second trigger may be initiatedduring or after the first trigger. Thus, multiple triggers may be activesimultaneously.

In Step 304, the video camera 100 receives a user-initiated trigger. Auser-initiated trigger originates from the user or video camera 100itself. The user-initiated trigger may be manually created orautomatically created. Manually created triggers may be generated by thepressing of a button, a selection of a user input, a powering-on of thevideo camera 100, or other action by the user. For example, the user maypress a button (such as a trigger button or a begin-recording button) onthe video camera 100 to initiate a trigger. The trigger may beautomatically created upon the detection of a certain criteria (whichmay be known as a triggering event). Examples of a triggering event caninclude detection of the sound of a gunshot or other loud noise,detection that sirens have been activated, entering or leaving of acertain geographic area, detection of the drawing of a firearm orelectronic weapon, detection of the beginning of a breath analysis orother external device use, detection of a vehicular collision or otherdriving event, detection of an elevated heart-rate or step-rate by theuser, detection of a certain speed or orientation of the video camera100 (or a rate of change thereof), or the detection of some othercriteria that may be indicative that the video data collected may be ofpotential future relevance. Yet another automatic user-initiated triggercould be the loss of communication with the video collection manager126. The video camera 100 will be sending the below-discussed periodicmetadata messages via the mobile broadband modem 122 or other wirelesscommunication element. If an acknowledgement is not received from thevideo collection manager 126, a recording or tagging could be triggeredby the lack of an acknowledgement (or after a couple of attempts). Forexample, if the user went out of transmission range such as in abuilding, basement, or other, the video camera 100 would ultimately betriggered to record or otherwise tag the video data. It should beappreciated that in some instances the user-initiated trigger isproduced locally (e.g., on the actual video camera) and in someinstances the user-initiated trigger is produced via the mobilebroadband modem 122 or other type of I/O unit.

In Step 306, the video camera 100 receives an administrator-initiatedtrigger. Administrator-initiated triggers originate from a systemadministrator, dispatcher, supervisor, or other person that is remotefrom the video camera 100 and associated with the system (and/or theentity utilizing the system), or from the system itself. As above, theadministrator-initiated trigger may be manually created or automaticallycreated. The administrator may manually create the trigger byinstructing the video collection manager 126 to send a trigger to all orsome of the video cameras. As an example, the administrator monitoring asituation may trigger all video cameras in a certain geographic areasuch that all begin recording and/or tag the already recording data. Asanother example, if the dispatcher knows that a user is in a situationwhich should trigger the video camera 100, but the user has forgotten toinitiate, the administrator can initiate the trigger remotely. The videocollection manager 126 may automatically create the trigger based uponthe occurrence of certain conditions. For example, if the videocollection manager 126 receives a user-initiated trigger from a firstvideo camera, the video collection manager 126 may automaticallygenerate a trigger for a second video camera that is in proximity to thefirst video camera (or which may come into proximity at a later time).

In Step 308, the video camera 100 receives a third-party initiatedtrigger. Third-party-initiated triggers originate external to thesystem. In some embodiments, the third-party-initiated trigger may begenerated externally to the system and sent to the system as a trigger.In other embodiments, the third-party-initiated trigger may be generatedby the system in response to external information. For example, thetrigger may be generated based upon information from a weather service(such as the National Weather Service), an earthquake detection system,an alerting system (such as an Amber Alert, a Silver Alert, a NationalEmergency Alert), or other system. The third-party may also be a similarsystem that is outside the control of the system. For example, a systemthat operates a city's fire department video system may generatethird-party-initiated triggers for a separate but similar system thatoperates that city's police department video system. In someembodiments, the third-party-initiated trigger may be received anddistributed by the video collection manager 126. In other embodiments,the third-party-initiated trigger may be sent to the video camera 100directly from the external source.

In Step 310, the video camera 100 initiates recording based upon one ormore of the above-discussed triggers. As discussed above, video datawill be stored in the non-volatile memory 116 of the video camera 100,such that all or a portion of the video data may be subsequentlytransferred. The video camera 100 is used to record events as seen froma first-person perspective of the wearer, the vehicle in which thecamera is mounted, the permanent mounted location of the camera, orother location. This can be advantageous for recreating anddemonstrating what happened at a later date. For example, if the wearerobserves a crime, an accident, or an event or function being performed,this can be observed later by others via the video. Because theindication that such an event needs to be recorded may come from theuser, the administrator, or some third party, the triggering of thevideo recording, saving, and/or tagging may be originating fromdifferent entities. As such, in embodiments of the invention, the videocamera 100 is configured to send triggering indications, receivetriggering indications, send periodic metadata messages, and performother functions relative to the video collection manager 126.

In embodiments of the invention, the video camera 100 will recordcontinuously throughout the work shift (or similar time period). Thevideo camera 100 may contain enough battery life in power supply 110 andenough memory in a camera-memory unit to record at least one day's worthof events. The wearer can utilize a “mark” button on the video camera100 to denote important events or observations that may be worthy oflater review and retention. The wearer may also perform an audibletagging by saying a certain phrase that is interpreted as being a mark,such that the wearer need not push a mark button. The audible taggingmay also be automatic, such as by being triggered by very loud noisescaptured. The video data captured by the video camera 100 may be storedinternally and/or transferred to the camera dock as discussed below. Thevideo data may then be selectively stored and/or transferred based uponthe tags in the video data, a retention policy of the system, a “firstin, first out” (“FIFO”) buffer, or other criteria. These functions maybe performed in addition to the sending and receiving of metadatamessages, triggers, and other information about the video data.

Other examples of parameters associated with the camera that may be usedto determine recording, tagging, and/or post-proceeding deletion ofrecorded data include a time of day when the data is being recorded, theuser and privileges associated with the user, a memory capacity of aparticular camera, a type of or location of the video camera 100 (e.g.,a head-mounted camera may be assigned different recording and processingfeatures than a vehicle-mounted camera), etc.

In Step 312, the video camera 100 sends periodic metadata messages tothe video collection manager 126. The video camera 100 may send theperiodic metadata messages directly to the video collection manager 126,via the mobile broadband modem 122 (or other wireless communicationelement) or indirectly to the video collection manager 126, via themobile broadband modem 122 and a recording device manager 200 or otherdevice. The wireless communication element may be a mobile broadbandmodem 122 (as discussed above), a Wi-Fi transceiver, a Bluetoothtransceiver, or other structure configured to communicate wirelessly.

The mobile broadband modem 122 allows the video camera 100 to remain incommunicative contact with the video collection manager 126 as the videocamera 100 travels. Because mobile broadband connections are moreextensively available in most areas, this allows the video camera 100 toremain in communicative contact over a large area. This allows the videocamera 100 to send status messages, metadata messages, trigger messages,and other information. This also allows the video camera 100 to receivestatus messages, metadata messages, trigger messages, and otherinformation from the video collection manager 126. Further, this allowsthe video collection manager 126 to track the locations and recordingstatuses of various video cameras, and to instruct recording and/ortagging based upon a trigger.

Various types of metadata may be associated with the video data.Metadata may provide information related to how the recording started,who started the recording, how the recording stopped, who stopped therecording, etc. Broadly, metadata may include beginning of the recordingmetadata (such as user information, who started the recording, how therecording started, a timestamp for the beginning of the recording, alocation stamp for the beginning of the recording, an event identifierreceived or generated, a status of the hardware, trigger information,external associated camera information, etc.), ongoing metadata duringthe recording (such as speed during the recording, location during therecording, orientation of the video camera 100 during recording, andother information), end of the recording metadata (such as how therecording stopped, who stopped the recording, a time stamp for the endof the recording, a location stamp for the end of the recording, whetherthe recording ended due to loss of power), and post-recording metadataadded manually by the user and/or the administrator.

Examples of metadata broadly include header metadata, internal eventtriggering metadata, external event triggering metadata, frame headermetadata, frame metadata, GPS location metadata, streaming metadata,camera monitoring metadata, checksum metadata, microphone metadata,recording ended metadata, event profiling metadata, Bluetooth metadata,output trigger metadata, dock metadata, video collection managermetadata, and system health metadata. It should be noted that the aboveare example groupings or types of metadata and that other groupings ortypes may be used. Examples of these groupings or types are discussed inmore depth below.

As a first example, header metadata may include a device firmwareversion, a metadata format version, a device serial number, a devicetype, a vehicle identification number associated with the device, a usernumber, a user name, a date stamp, a time stamp, an event identificationnumber, an event name, an event description, an incident or case number,a video stream count, an audio stream count, and the like.

As a second example, internal event triggering may include accelerationdata, speed data, braking data, cornering data, collision data, GPSlocation data, button press on device data, button press on a remotedata, power loss data, vertical threshold data, event continuation data.As a third example, external event triggering may include any number ofexternal sensors that may be providing data.

As a fourth example, frame header metadata may include frameidentifiers, offset, frame type, data length, and other datainformation. As a fifth example, frame metadata may include vehiclespeed, GPS latitude, GPS longitude, GPS valid or not, number of GPSsatellites, distance from home base, distance from some other location,patrol, lock, target, accelerometer readings, and external sensorreadings. As a sixth example, GPS location metadata may include any ofnumerous unauthorized location information such that the proximity tothose unauthorized locations may be determined. Similarly, the GPSlocation metadata may include waypoints, dispatch locations,headquarters locations, locations of interest, and other locations.

As a seventh example, the streaming metadata may include stream number,video source, audio source, left audio source, right audio source,day/night mode, camera type, zoom level, flags, bitrate, video active,video monitored, lights, IR lights, covert mode, and camera numbers.

As an eighth example, the checksum metadata may include a file name, ahash type, and the checksum itself. As a ninth example, the microphonemetadata may include a serial number of the microphone, a GPS locationof the microphone, a stream number, a status, and an audio feed status.As a tenth example, the recording ended metadata may include an end timestamp, an end date stamp, a method of ending (such as stop button, postevent, file size limit, video signal lost, power off by user, lowbattery power off, external command, etc.).

As an eleventh example, the event profiling metadata may includeinformation related to a subject of the video (such as age, gender,ethnicity, and other distinguishing characteristics) and may include areference or identification number for the subject. As a twelfthexample, the Bluetooth metadata may include information related toBluetooth activation and/or deactivation, Bluetooth connection status,Bluetooth signal strength, Bluetooth connection established timestamp,Bluetooth connection lost timestamp, and other information related to aBluetooth connection. As a thirteenth example, the dock metadata mayinclude information related to a dock into which the camera was placedafter the recording was completed. The dock metadata may include a docktype, a dock serial number, a dock firmware version, a user nameassociated with the dock, a docking timestamp, etc. The video collectionmanager metadata may include video collection manager type, a videocollection manager serial number, a video collection manager firmwareversion, a vehicle and/or user associated with the video collectionmanager, an event identifier supplied by the video collection manage, anoffset time, a record of the instruction to begin recording, a record ofthe instruction to end recording, a status update from the videocollection manage, and other information related to the video collectionmanager 126.

As a fourteenth example, the system health metadata may be independentof any particular video event. System health metadata is a record ofsystem operations, statuses, and other information. The system healthmetadata is recorded in a log file that can be used to determine thecause of a system failure.

Because at least a portion of the metadata is being sent to the videocollection manager 126 via the mobile broadband network 124, theadministrator can be alerted to various conditions and take actionaccordingly. For example, if the user manually stopped the recording,the administrator may reinstate the recording and/or lock the user outof ending the recording. As another example, the recording may stop onlyupon the administrator approving the stopping of the recording. As stillanother example, the administrator may create a geofence or otherlocation information remotely that affects the operation of the camerain relation to that location (e.g., no users may manually stop recordingwithin 200 yards of the designated location).

In Step 314, the trigger terminates. The trigger my terminate in any ofnumerous ways. For example, the user may terminate the trigger, such asby pressing the mark button again or providing another user input. Asanother example, the administrator may terminate the trigger based upona resolution of the situation that caused the trigger to be initiated.As yet another example, the trigger may be terminated upon the passageof a certain period of time, the movement of the video camera 100 intoor out of a certain location, an audible cue by the user, the removal orending of the condition that initiated the trigger, or otherinformation.

In Step 316, the video camera 100 sends a trigger-complete metadatamessage to the video collection manager 126. The trigger-completemetadata message may be indicative that the trigger complete message wasreceived, the video camera 100 is complying with the trigger completemessage, that the video recording has ceased, that the trigger wascompleted locally by the user, or other indication. The trigger-completemetadata message may be a periodic metadata message. Further, thetrigger-complete metadata message may include metadata regarding therecording that is available upon completion.

In Step 318, the video camera 100 stores the video data. This mayinclude recording the video data in the non-volatile memory 116,transferring the video data (or a portion thereof) via the I/O port orthe mobile broadband modem 122, transferring the video data (or aportion thereof) to the computer 210 or to another external computingdevice.

Turning to FIG. 4, various messages via the mobile broadband network 124between the video camera 100 and the video collection manager 126 areshown. It should be appreciated that, as with other steps discussedherein, the steps described herein are not necessarily in order: not allsteps need be performed in all embodiments, steps may be performed inany order, some steps may be performed simultaneously, some steps may beperformed more than once, etc.

In Step 400, the video camera 100 and the video collection manager 126establish wireless electronic communication via the mobile broadbandmodem 122. The video collection manager 126 receives and processesinformation from the video camera 100 upon the connection beingestablished. This allows for secure and automatic transfers ofinformation. If the connection is lost, or if the transfer isinterrupted, the information may be saved at the video camera 100 andtransferred upon a reconnection. The files transferred may also belogged for a complete audit trail.

In Step 402, the video camera 100 sends a first status message to thevideo collection manager 126 via the mobile broadband modem 122. Forexample, the first status message may include location, speed,orientation, recording status, trigger status (whether any trigger hasbeen received or is otherwise active), associated user information,associated device information, and other status information. The videocamera 100 sends a second status message, and other subsequent statusmessages. In some instances, the second or subsequent status message mayinclude information that has changed since the previous status message.For example, if the location and speed have changed since the previousstatus message, this information will be sent while other informationthat has not changed, such as associated device information, may not besent or may be abbreviated. The second or subsequent status message maybe delayed from the first status message by a certain time interval(such as ten seconds, thirty seconds, one minute, ninety seconds, twominutes, or other interval), or by a change in the information sent, orboth.

In Step 404, a trigger indication is generated. As discussed above, thetrigger indication may be initiated at the user, an administrator (suchas the video collection manager 126 itself), or a third party. Thetrigger indication is sent from the generating device to the otherdevice (e.g., from the video camera 100 to the video collection manager126, or from the video collection manager 126 to the video camera 100).The trigger indication therefore ensures that both devices haveinformation that a trigger has been or should be initiated.

In Step 406, a trigger confirmation message is sent by the video camera100 to the video collection manager 126. The trigger confirmationmessage may indicate receipt of the trigger message, the beginning ofrecording of video data, the storing of the recording of video data, theannotation of otherwise recorded video data, or some other indication tothe video collection manager 126 that the video camera 100 is complyingwith the trigger message. The video camera 100 may also send periodictrigger confirmation messages indicative that the video camera 100considers the trigger to still be active. This allows the videocollection manager 126 to terminate the trigger at a certain time (orupon some other criteria).

In Step 408, periodic metadata messages are sent to the video collectionmanager 126 during the trigger. This allows the video collection manager126 to continue to track the location, recording status, and otherstatus information for the video camera 100. The periodic metadatamessages may include any combination of header metadata, internal eventtriggering metadata, external event triggering metadata, frame headermetadata, frame metadata, GPS location metadata, streaming metadata,camera monitoring metadata, checksum metadata, microphone metadata,recording ended metadata, event profiling metadata, Bluetooth metadata,output trigger metadata, dock metadata, video collection managermetadata, and system health metadata (as discussed above).

In Step 410, a trigger termination message is sent from the videocollection manager 126 to the video camera 100 via the mobile broadbandnetwork 124. As discussed above, the trigger may be terminated in any ofnumerous ways. For example, the administrator may terminate the triggerbased upon a resolution of the situation that caused the trigger to beinitiated. As yet another example, the trigger may be terminated uponthe passage of a certain period of time, the movement of the videocamera 100 into or out of a certain location, an audible cue by theuser, the removal or ending of the condition that initiated the trigger,or other information.

In Step 412, a trigger-complete metadata message may be sent to thevideo collection manager 126. The trigger-complete metadata message mayinclude a checksum and other information about the video data, such asthe length of the recording, locations associated, and otherinformation. The trigger-complete metadata message may be utilized bythe video collection manager 126 to determine what video data to requestfrom the camera dock or directly from the video camera 100. In this way,the video collection manager 126 generates a list of what video data wasrecorded and a list of what video data is coming. This can also includea status of transmission of the video data and information on what videodata is being transmitted. Thus, chain of custody of the video data isimproved over prior art systems.

In Step 414, a retention instruction message is sent from the videocollection manager 126 to the video camera 100. In other embodiments,the retention instructions may be standardized or based upon some otherset criteria. In embodiments, the video data related to the trigger istransferred to the video collection manager 126, either directly or viathe camera dock. This step may be performed at a later time, such asupon the video camera 100 being returned to the camera dock or to aWi-Fi connection, or may be performed immediately (such as upon arequest from the administrator or video collection manager 126 in anemergency situation). The video data may be automatically tagged andassigned to an incident identification number (such as provided by thevideo collection manager 126). In some embodiments, an original videofile is saved separately from any tagged or edited video file, so as tomaintain integrity and security of the video data. The tagging allowsthe video data to be catalogued with other video data (from the sameand/or different video cameras) without requiring the user and/or theadministrator to manually catalogue. Examples of cataloguing and sortinginclude: user name, time, date, vehicle or camera identifier, prioritylevel, status, workflow state, incident number, “triggered by”information, event identification, frame triggers (such as speed,acceleration, emergency lights, sirens, etc.). Other activity related tothe video may also be logged, such as viewing, outputting, commenting,tagging, editing, removing, and archiving of the video data.

In embodiments of the invention when a user-initiated trigger isreceived (e.g., a mark button is pressed), the video camera 100 sendsmetadata, a still image, audio data, or other information to the videocollection manager 126. This may be used to alert an administrator ofthe trigger, to allow for administrator-initiated triggers to be sent toother video cameras, or to perform other functions. For example, themetadata may include a location where the trigger initiated, the time ofthe trigger, the orientation of the camera during the trigger, and otherinformation related to the camera or the image. Other examples includethe speed of the vehicle associated with the video camera 100; othervehicle information (such as an OBD2 monitor or collision sensor); andthe activation or deactivation of sirens, lights, brakes, microphones,and other devices.

In some embodiments, upon a press of the mark button the video camera100 may start live streaming the audio data, periodic still images, orvideo data to the video collection manager 126 for immediate review(such as in an emergency situation). This may be done at the request ofthe security administrator (e.g., a remotely given command via the videocollection manager 126) or by an indication from the wearer such as along press, a series of multiple presses of the mark button, or by acertain audible mark.

Other functions may also be performed based upon the information sent tothe video collection manager 126. As an example, upon the initiation ofa trigger during a traffic stop, the video camera 100 may upload all ora portion of the audio data collected. The audio data sent to the videocollection manager 126 may be processed such that certain informationmay be obtained, a transcript of the audio data is automaticallygenerated, or other functions performed. Based upon the informationobtained, an incident report or ticket may be at least partially createdor completed. This incident report or ticket may then be sent to theuser to assist the user in performing job duties.

As a more specific example, the video collection manager 126 (havingreceived the audio data from the video camera 100) may determine thatthe user said, “I observed you driving through that stop sign withoutstopping.” Based upon this analysis, the video collection manager 126may at least partially complete the ticket (e.g., select the correctform and add the specific offense), or may send the information to acomputer system in the user's vehicle to perform this function (such ascomputer 210). The analysis of the audio data may be too computationallyintensive to be performed at the video camera 100 or the computer systemin the vehicle (such as computer 210), and/or may require internet-basedresources to be performed. Other information may also be automaticallyadded to the ticket, such as the user's name, the location of thetrigger, the time of the trigger, and other information based upon themetadata.

As another example, a still image of the rear of the vehicle may beautomatically sent to the video collection manager 126. Based upon this,the video collection manager 126 may perform an optical characterrecognition (“OCR”) on the still image to determine the license platenumber of the vehicle. This information may be used access a database oflicense plate numbers and/or to fill out at least a portion of theticket. In other embodiments, the OCR may be performed locally, and thisinformation sent to the video collection manager 126 with the triggerindication and/or the periodic metadata message.

As still another example, a still image of a person's face (such as froma body-worn video camera 100) may be uploaded for facial recognition ofthat person. This may be performed automatically (e.g., upon eachencounter with a person), upon a user-initiated request (e.g., upon asuspicion that fake identification documents have been provided), uponan administrator-initiated request (e.g., subsequent to the recording ofthe image, upon an emergency situation involving that person such as afleeing of the scene), or upon a third-party-initiated request.

In some embodiments of the invention, the video collection manager 126is a dedicated device that communicates with the video camera 100 and/orthe camera docks. In other embodiments, the video collection manager 126is a remote application operating on a server (such as a cloud-basedvideo collection manager). In still other embodiments, the videocollection manager 126 is a local application operating on a computersystem associated with the facility or organization that administers thevideo collection system.

In embodiments of the invention, the video collection manager 126receives the above-discussed messages directly from the video camera 100and later requests video data related to at least one message from thecamera dock. The video collection manager 126 may be communicativelycoupled to the camera dock directly or indirectly. Examples of directcommunication include a wired or wireless connection between the videocollection manager 126 and the camera dock. Indirect connection includesan intermediary device for facilitating the communication. For example,the camera dock may be communicatively coupled to a computer, which inturn communicates with the video collection manager 126. As anotherexample, the camera dock may include a Wi-Fi connection that connectsthrough a wireless router to the video collection manager 126, or amobile broadband connection.

In embodiments of the invention, the camera dock sends at least aportion of the video data to the video collection manager 126. Thecamera dock will upload the video data associated with metadata asrequested by the video collection manager 126 and/or based upon certainconditions and criteria associated with the metadata. These conditionsmay be previously determined or set by the video collection manager 126(or an administrator operating the video collection manager 126 orassociated computer platform). The metadata may the upload of certainvideo data. For example, metadata that may trigger an upload include along press of the mark button, any press of the mark button, a GPSlocation, or entry into an unauthorized or abnormal location. As anexample, a human operator or automatic process of the video collectionmanager 126 may manage the available upload bandwidth to prioritize theupload of certain information (e.g., video data) based upon theabove-discussed characteristics. Based upon the number of body-mountedcameras in the docks, and the amount of video data to potentially beuploaded, the video collection manager 126 may direct what video datawill be uploaded and an order for upload, what video data should beretained on the local body-mounted camera and/or camera dock, what videodata should be deleted, etc.

It should be appreciated that various embodiments of the invention couldbe applied to numerous fields. Examples of the fields of use include lawenforcement, emergency response, government vehicle fleets, commercialvehicle fleets, schools, hospitals, commercial warehouses, and otherfields of use that use distributed video cameras.

It should be appreciated that, while the above disclosure is directedmainly to the field of law enforcement, some embodiments of theinvention are associated with other fields. Some embodiments of theinvention are directed to military functions, para-military functions,private security functions, private citizens, etc. For example, the user22 may be a private citizen and the subject may be an assailant or othermalfeasant. The law enforcement field discussed is merely exemplary andshould not be construed as limiting.

Another exemplary field of usage for embodiments of the invention willnow be discussed. An application-based taxi service may utilizeembodiments of the invention for managing drivers. The administrator maysend (automatically or manually) information to the driver regarding acertain trip, including a unique trip identifier. The suppliedinformation may also include a pickup time and location, a drop offlocation, an expected distance, monetary compensation for the driver,information about the passenger, and other information that may bepertinent to the trip. The video camera 100 may begin recording uponpickup and end recording upon drop off. The beginning and ending of thevideo, the marking with a unique trip identifier associated with thepassenger, and the uploading of metadata and/or video data are performedwithout any additional steps or input from the driver. This providesadditional security for both driver and passenger.

Although the invention has been described with reference to theembodiments illustrated in the attached drawing figures, it is notedthat equivalents may be employed, and substitutions made herein withoutdeparting from the scope of the invention.

Having thus described various embodiments of the invention, what isclaimed as new and desired to be protected by Letters Patent includesthe following:
 1. A method of managing video data captured by a videocamera, the method comprising: receiving a trigger message indicative ofa trigger; in response to receiving the trigger message, transferringvideo data captured by the video camera from a volatile memory to anon-volatile memory; storing subsequently recorded video data from thevideo camera in the non-volatile memory; and transmitting a messageassociated with the video data to a remote video collection manager,wherein the message comprises trigger metadata indicative of the triggerthat triggered storage of the video data in the non-volatile memory. 2.The method of claim 1, further comprising the steps of: receiving aninstruction from the remote video collection manager; responsive to theinstruction, transmitting the video data to the remote video collectionmanager; and storing the video data in a remote data store.
 3. Themethod of claim 2, wherein the message and the video data aretransmitted over a wireless network.
 4. The method of claim 1, furthercomprising the step of sending a status message to the remote videocollection manager, wherein the status message comprises informationindicative of the availability of the video camera.
 5. The method ofclaim 1, wherein the trigger is a manual user-initiated trigger receivedfrom a user operating the video camera.
 6. The method of claim 1,wherein the trigger is an automatic trigger based on criteria detectedat the video camera.
 7. The method of claim 1, wherein the trigger is anadministrator-initiated trigger received in response to anadministrative user remote from the video camera.
 8. A system formanaging video data, the system comprising: a remote video collectionmanager; and a video camera comprising: a volatile memory; anon-volatile memory; and a processor programmed to: receive a triggermessage indicative of trigger; in response to receiving the triggermessage, transfer video data captured by the video camera from thevolatile memory to the non-volatile memory; and send a messageassociated with the video data to the remote video collection manager,wherein the message comprises trigger metadata indicative of the triggerthat triggered storage of the video data in the non-volatile memory. 9.The system of claim 8, wherein the remote video collection manager ishosted on a computing device disposed in a back-end office.
 10. Thesystem of claim 9, wherein the video camera is a body-mounted videocamera worn by a law enforcement officer.
 11. The system of claim 10,wherein the trigger message is received remotely from the back-endoffice.
 12. The system of claim 9, wherein the video camera is avehicle-mounted video camera disposed on a vehicle.
 13. The system ofclaim 12, wherein vehicle information including at least one of vehiclespeed, location data, or acceleration data is stored within framemetadata of the video data.
 14. The system of claim 8, wherein thenon-volatile memory is removably mounted within the video camera.
 15. Avideo camera for capturing video data, the video camera comprising: avolatile memory; a non-volatile memory; and a processor programmed to:receive a trigger message indicative of trigger; in response toreceiving the trigger message, transfer video data captured by the videocamera from the volatile memory to the non-volatile memory; and send amessage associated with the video data to a remote video collectionmanager, wherein the message comprises trigger metadata indicative ofthe trigger that triggered storage of the video data in the non-volatilememory.
 16. The video camera of claim 15, further comprising a mobilebroadband modem for communicating with the remote video collectionmanager over a mobile broadband network.
 17. The video camera of claim15, wherein the message further comprises the video data.
 18. The videocamera of claim 15, wherein the video camera is one of a body-mountedvideo camera, a vehicle-mounted video camera, or a static mounted videocamera.
 19. The video camera of claim 18, wherein the video camera isassociated with a device-specific key and the device-specific key isassigned to the video data for authentication.
 20. The video camera ofclaim 15, wherein the video data is encrypted with an encryption key.